
<html><HEAD>
<LINK REL=STYLESHEET HREF="default.css" TYPE="text/css">
<TITLE>
About deploying applications</TITLE>
</HEAD>
<BODY>

<!-- Header -->
<p class="ancestor" align="right"><A HREF="apptechp239.htm">Previous</A>&nbsp;&nbsp;<A HREF="apptechp241.htm" >Next</A>
<!-- End Header -->
<A NAME="CDECBBIA"></A><h1>About deploying applications</h1>
<A NAME="TI6579"></A><p>PowerBuilder lets you develop and deploy applications for
many application architectures. </p>
<A NAME="TI6580"></A><h4>Traditional client/server applications</h4>
<A NAME="TI6581"></A><p>The primary focus of this chapter is on building an executable
file and packaging a single- or two-tier application for deployment.
The chapter helps you decide whether to use compiled code or pseudocode,
whether to use dynamic libraries (PBDs or DLLs) and how to organize
them, and whether to deploy resources such as bitmaps and icons
separately or use a PowerBuilder Resource file (PBR).</p>
<A NAME="BABDJEBJ"></A><h4>Internet and distributed applications</h4>
<A NAME="TI6582"></A><p>When you build a client in a multitier application, you need
to make many of the same choices as you do for a traditional client/server
application. If you are building <ABBR title = "e a server" >EAServer</ABBR> or
COM components, you need to know about PowerBuilder dynamic libraries
(PBDs) and PBRs, described in <A HREF="apptechp241.htm#BJFBGHBG">"Learning what can go in
the package"</A>. </p>
<A NAME="TI6583"></A><h4>For more information</h4>
<A NAME="TI6584"></A><p>For detailed information about the files you need to deploy
with client/server, multitier, and Web applications, see <A HREF="apptechp243.htm#CFHBBAEA">Chapter 37, "Deploying Applications
and Components."</A></p>

